Skip to content

fix(docs): section-URL 404s + Python capabilities page#391

Merged
pratyush618 merged 2 commits into
masterfrom
fix/docs-getting-started-404
Jul 8, 2026
Merged

fix(docs): section-URL 404s + Python capabilities page#391
pratyush618 merged 2 commits into
masterfrom
fix/docs-getting-started-404

Conversation

@pratyush618

Copy link
Copy Markdown
Collaborator

Fix docs "Page not found" on section URLs + add Python capabilities page

Two docs fixes.

1. Index-less section URLs 404

Sections that have child pages but no landing/index page — each SDK's getting-started, and resources — 404'd on a bare hit. This is reachable from the breadcrumb: on any …/getting-started/quickstart page the "Getting Started" crumb links to the bare /<sdk>/getting-started, which had no page → "No documentation page matches this URL." (affects every SDK).

Fix: redirect these bare section URLs to the section's first page via the existing static-redirect mechanism (prerendered stub + SPA client-nav):

  • /{node,python,java}/getting-started…/getting-started/installation
  • /resources/resources/comparison

2. Python getting-started missing "Capabilities at a glance"

The Node and Java SDKs have a capabilities page in getting-started; Python didn't. Added python/getting-started/capabilities.mdx (a feature → guide map, mapped to Python's actual guide URLs) and listed it in the section's meta.json.

Verification

biome check + typecheck clean; full docs build succeeds — the four redirect stubs prerender with the correct meta-refresh targets, and python/getting-started/capabilities prerenders.

Sections with child pages but no landing page (each SDK's getting-started, and resources) 404'd on a bare hit — e.g. clicking the "Getting Started" breadcrumb crumb. Redirect them to the section's first page.
Python's getting-started was missing the capabilities overview the other SDKs have. Maps each feature to its Python guide.
@github-actions github-actions Bot added the docs label Jul 8, 2026
@coderabbitai

coderabbitai Bot commented Jul 8, 2026

Copy link
Copy Markdown

Warning

Review limit reached

You’ve reached a temporary PR review limit under our Fair Usage Limits Policy.

Your recent review volume is higher than typical usage, so adaptive limits are currently applied.

Next review available in: 3 minutes

Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available.
You're only billed for reviews past your plan's rate limits ($0.25/file).

How can I continue?

After more reviews become available, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews.

How do review limits work?

CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability.

For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window.

Please refer docs for additional details.

Review details
⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro

Run ID: d488b9ad-6c36-46fa-bf79-16f23beb249f

📥 Commits

Reviewing files that changed from the base of the PR and between 8534309 and dd3f248.

📒 Files selected for processing (3)
  • docs/app/lib/redirects.ts
  • docs/content/docs/python/getting-started/capabilities.mdx
  • docs/content/docs/python/getting-started/meta.json
✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Commit unit tests in branch fix/docs-getting-started-404

Comment @coderabbitai help to get the list of available commands.

@pratyush618
pratyush618 merged commit 6f90331 into master Jul 8, 2026
14 checks passed
@pratyush618
pratyush618 deleted the fix/docs-getting-started-404 branch July 8, 2026 04:03
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant